home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
remote
/
u_orig.zip
/
U-ORIG.DOC
< prev
next >
Wrap
Text File
|
1992-07-07
|
4KB
|
79 lines
* User-defined Origin lines for Remote Access
Fredric L. Rice
FidoNet 1:102/890.0 - The Skeptic Tank.
One of the more noted comments one will hear every now and then in the
Echo Conferences is that the origin lines of Users do not reflect the
moods and opinions of the User yet will usually reflect the moods and
opinions of the System Operator. This is actually an artifact of the
application of 'clever' sayings and remarks being used in the origin
line rather than the name of the system as it seems was originally
intended. Indeed, you might recall a few comments in FidoNews about
the fact that the origin lines are being somewhat 'abused.'
Well good. Let's abuse them some more. To my knowledge, there is no
utility, door or otherwise, which allows Users to tailor their origin
lines for the Remote Access systems they're posting messages with. For
this ability, I've developed a DOOR program which will allow Users to
enter any origin they wish, provided it is from 10 to 60 characters in
length and their security rating is of a certain value or higher.
How it works:
To offer a description of the process, let me describe how it works on
my system. Your system may choose a different route, of course, due to
the very good flexibility of Remote Access.
1) My WELCOME.* files have the following control sequence in them:
^X *C /C U-ORIG APPLY
This will cause the U-ORIG program to open up the DORINFO1.DEF file
and extract the Users name, com port, and security value. The program
will also extract configuration information out of a file called
U-ORIG.CFG which contains:
o A default origin line
o A minimum security level value
o The path to the Remote Access root directory
If the security values don't match or allow the User to apply his or
her own origin line, then the program exits back to Remote Access. If
the security value allows it, the Users origin line (if there is one
yet) is extracted from the U-ORIG.DAT file and written into each one
of the active message folders in the MESSAGES.RA data file. If the
User doesn't have an entry, the default origin line in the U-ORIG.CFG
file is used. This makes sure that a User does not get someone elses
origin line applied to his or her messages.
2) The User may select a menu option which will execute the following:
*M C:\FRED\U-ORIG UPDATE
The program is executed as before only this time, the User is offered
a display of their old origin line (if there is one) and is prompted
about whether it should be change or if a new one should be created.
There is a 30 second time-out on the inputs so that if something goes
wrong, U-ORIG will return to the Remote Access BBS after 30 seconds.
After entering an origon line, the User may (K)eep, (T)ry again, or
(Q)uit all together. If the User elects to Keep the new origin line,
the origin line is saved to the U-ORIG.DAT file along with the Users
name, and the new origin line is applied to the message folders,
allowing any messages entered to have the new origin lines applied.
There is another option and that is to execute U-ORIG without any
option offered on the command line. When this is done, the program
will simply update all of the active message folders with the default
origin line stored in the U-ORIG.CFG data file.
U-ORIG.LZH is available here for FileRequest and contains the source
code (Written in Borlan C 2.0) so that if you find that it does things
you don't like, you may change the code. If you have an update in mind
or need something done to your particular version, let me know and I
will work with you on it and FileAttach the update for free.
Fredric L. Rice
1:102/890.0. The Skeptic Tank.